docs: wallet_account derivation-path fields for export policies - #768
Draft
andrewkmin wants to merge 2 commits into
Draft
docs: wallet_account derivation-path fields for export policies#768andrewkmin wants to merge 2 commits into
andrewkmin wants to merge 2 commits into
Conversation
Document six new wallet_account policy-language fields (path, path_indexes, path_hardened, wallet_id, curve, address_format) added for EXPORT_WALLET_ACCOUNT activities, plus a hardened derivation-subtree export policy example.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Adversarial-review follow-ups: - Clarify that referencing the new wallet_account derivation-path fields on activities other than EXPORT_WALLET_ACCOUNT produces a MissingField evaluation error (policy outcome is an error), not empty values. - Add version-skew rollout guidance: an erroring EFFECT_DENY is skipped while a broad EFFECT_ALLOW still matches (fails open during the skew window) - recommend narrow-allow patterns over broad-allow + path-deny.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents six new
wallet_accountpolicy-language fields being added in a companion tkhq/mono PR (attested derivation-path fields forEXPORT_WALLET_ACCOUNT):path(string) — the account's BIP32 derivation path as storedpath_indexes(list) — child indexes with the hardened bit strippedpath_hardened(list) — positionally paired hardened flagswallet_id(string) — ID of the wallet the account belongs tocurve(string) — curve enum nameaddress_format(string) — address format enum nameChanges:
features/policies/language.mdx: six new rows in the Wallet Account struct table, plus a note explaining that single-quoted policy literals cannot contain'(why paths are exposed structurally) and that these fields are currently populated only forEXPORT_WALLET_ACCOUNTactivities.features/policies/examples/access-control.mdx: example policy restricting exports to a fully-hardened 4-segment subtree (Spark-purpose example), with an ed25519 caveat.Companion mono PR: policy: expose attested derivation-path fields on wallet_account for EXPORT_WALLET_ACCOUNT (link TBD).
Do not merge before the mono PR ships.